Clarify sensitive data handling in security model#70424
Open
bharatkhanna-dev wants to merge 2 commits into
Open
Clarify sensitive data handling in security model#70424bharatkhanna-dev wants to merge 2 commits into
bharatkhanna-dev wants to merge 2 commits into
Conversation
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
|
1 task
bharatkhanna-dev
marked this pull request as ready for review
July 25, 2026 03:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Clarify the sensitive-information section of the security model so it matches Airflow 3's current behavior.
Why
The previous wording said sensitive information would not be exposed through the API, UI, or
airflowctl, while the same section documented authorized access through the Task Execution API. The updated wording distinguishes default masking from authorized execution-time access and makes the CLI behavior explicit.Validation
git diff --checkThis is a documentation-only change; no runtime behavior is affected.
Closes #59839
Generative AI disclosure
Generative AI tools were used to help research the issue, draft the wording, and prepare this pull request. I reviewed the final change and validation results.